Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1182

reference: 125-tree-1
name: 1182
tree-preservation-order: undefined
125-tpo-1
uprn
address-text
point: POINT (-1.030054 50.866690)
geometry: MULTIPOLYGON (((-1.030012 50.866685,-1.030014 50.866693,-1.030020 50.866701,-1.030029 50.866707,-1.030041 50.866711,-1.030054 50.866712,-1.030067 50.866711,-1.030089 50.866702,-1.030095 50.866694,-1.030097 50.866686,-1.030095 50.866677,-1.030089 50.866670,-1.030080 50.866664,-1.030068 50.866660,-1.030055 50.866658,-1.030030 50.866663,-1.030020 50.866669,-1.030014 50.866677,-1.030012 50.866685)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL